Raspberry Pi End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Raspberry Pi versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
Raspberry Pi 500+ is supported until January 1, 2035, its end-of-support date. The next Raspberry Pi version to reach end of life is 400, on January 1, 2028. 3 of 24 tracked Raspberry Pi versions are past end of life; the most recent to reach it, Compute Module 1, did so on January 1, 2026. The full Raspberry Pi lifecycle, with every version's release and end-of-support date, is in the table below.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1 Model B | — | Mar 1, 2012 | Jul 14, 2014 | 4452 days past EOL | EOL |
| 1 Model A | — | Feb 4, 2013 | Nov 10, 2014 | 4333 days past EOL | EOL |
| Compute Module 1 | — | Apr 7, 2014 | Jan 1, 2026 | 263 days past EOL | EOL |
| 1 Model B+ | — | Jul 14, 2014 | Jan 1, 2030 | 1198 days remaining | Active |
| 1 Model A+ | — | Nov 10, 2014 | Jan 1, 2030 | 1198 days remaining | Active |
| 2 Model B | — | Feb 2, 2015 | TBD | Supported | Active |
| Zero | — | Nov 26, 2015 | Jan 1, 2030 | 1198 days remaining | Active |
| 3 Model B | — | Feb 29, 2016 | Jan 1, 2028 | 467 days remaining | Active |
| Compute Module 3 | — | Jan 16, 2017 | Jan 1, 2028 | 467 days remaining | Active |
| Zero W/WH | — | Feb 28, 2017 | Jan 1, 2030 | 1198 days remaining | Active |
| 3 Model B+ | — | Mar 14, 2018 | Jan 1, 2030 | 1198 days remaining | Active |
| 3 Model A+ | — | Nov 15, 2018 | Jan 1, 2030 | 1198 days remaining | Active |
| Compute Module 3+ | — | Jan 28, 2019 | Jan 1, 2028 | 467 days remaining | Active |
| 4 Model B | — | Jun 24, 2019 | Jan 1, 2034 | 2659 days remaining | Active |
| Compute Module 4 | — | Oct 19, 2020 | Jan 1, 2034 | 2659 days remaining | Active |
| 400 | — | Nov 2, 2020 | Jan 1, 2028 | 467 days remaining | Active |
| Pico | — | Jan 21, 2021 | Jan 1, 2036 | 3389 days remaining | Active |
| Zero 2 W | — | Oct 28, 2021 | Jan 1, 2030 | 1198 days remaining | Active |
| Compute Module 4S | — | Apr 4, 2022 | Jan 1, 2034 | 2659 days remaining | Active |
| 5 | — | Oct 23, 2023 | Jan 1, 2036 | 3389 days remaining | Active |
| Pico 2 | — | Aug 8, 2024 | Jan 1, 2040 | 4850 days remaining | Active |
| Compute Module 5 | — | Nov 27, 2024 | Jan 1, 2036 | 3389 days remaining | Active |
| 500 | — | Dec 9, 2024 | Jan 1, 2034 | 2659 days remaining | Active |
| 500+ | — | Sep 25, 2025 | Jan 1, 2035 | 3024 days remaining | Active |
Live EOL badge for your README — updates automatically at every build.
[](https://endoflife.ai/raspberry-pi)
Raspberry Pi lifecycle status — the real story
Raspberry Pi's end-of-life commitments are about hardware production, not software. The company publishes an 'in production until at least' date for each board on its product page — Raspberry Pi 5, for example, will remain in production until at least January 2036 — and the dates above are those commitments. Software support is separate from that hardware commitment.
A board past its production date may still run a supported OS for years; what ends is availability of new units and the commitment to keep manufacturing them.
Verified against the vendor's lifecycle documentation on August 22, 2026.
Raspberry Pi release and support pattern
Of the 24 release lines tracked, 3 are past end of life and 21 are still within support. The newest line, 5-500+, was released September 25, 2025. The next scheduled end of life is 4-400 on January 1, 2028 — 467 days from this build. The longest-supported line currently published is pico2, to January 1, 2040.
Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.
What does Raspberry Pi end of life mean for your organization?
When a version of Raspberry Pi reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.
Organizations running EOL Raspberry Pi should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Your options when Raspberry Pi reaches end of life
There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.
| Option | Best when | Watch out for |
|---|---|---|
| Move to a supported version | The system will outlive the current version's support window and you can schedule the work | Budget for compatibility testing, not just the upgrade itself — that is where the real cost sits |
| Replace the component | The project is unmaintained, or a better-supported alternative exists | The replacement has its own lifecycle and its own end-of-life date — you are changing vendors, not escaping the problem |
| Commercial extended support | Not available for Raspberry Pi from the original maintainer | Third-party vendors patch some end-of-life software on a custom basis; availability depends on the specific version and source access |
| Document accepted risk | The system is isolated, short-lived, or scheduled for retirement | Only defensible with real compensating controls and a written decision — auditors treat undocumented end-of-life software as a finding |
How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.
Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →